Host.PROC was written because, quite frankly, I'm paranoid. Quite a while ago, I used to run Red Ryder Host nearly every night while I was at work, and in the evenings when I was sleeping. (I had really bad working hours back then).
One day that I should have been at work, but called in sick, somebody called. This criminal was trying to log in as SYSOP, SYS OP, SYSTEM, SYSTEM OPERATOR,... You know, all the usual names as well as variations of Tom, Thomas, Tommy, etc. Yet nowhere within RR Host was my real name or even my initials mentioned or even hinted at. Therefore I assumed it must have been someone who knew me who was trying to get in at the top level.
The passwords "He" was using was really shocking. If he only knew how close he was to getting the right password, I’m sure he would have kept it up all night.
Since access was limited anyway with RR Host, I wasn’t too concerned and I was also waiting for whoever it was to do something that would give them away. Besides, I was there watching, and once in between calls, I lowered everyone’s access level to ZERO. It was even kind of fun watching this bunghole make three attempts, only to get cutoff, and then call right back again. This went on for forty five minutes, and then every thirty to forty minutes after that, as new passwords were thought up. Yes, and all of it went into a HUGE Caller Log file.
So why am I bothering you with this story? Simple... As I said before, RR Host (and I’m sure Second Sight is the same), remote access is limited even for the Sysop. But!!! White Knight, if the Full Access password is guessed, your ENTIRE system is at risk!
Luckily, I’m not THAT paranoid. I still run WK host quite a lot, but now I use this “souped”* up version of Host.PROC. Now Host is on for only a minimum of time while I need access.
*I used to edit and recompile the start time in my original procedure every time I needed to use it. What a pain. I then thought I’d let everyone use it, since it seemed NOW anyway, much easier to use.
So far I haven't found a way to cancel the Host mode once it is started from within this procedure. All I can suggest is for you to call and "DO" a procedure that quits W.K., or sets "S" register zero to zero so that your modem won't answer. See AUTOANSWER OFF in your W.K. manual.
I guess I might need to invest in Second Sight, and maybe go public? For now though, W.K. Host is plenty for my needs.
